The DBMS must maintain the binding of security labels to information with sufficient assurance that the information/attribute association can be used as the basis for automated policy actions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32172	SRG-APP-000011-DB-000191	SV-42489r1_rule		Medium

Description
Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information system and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. Examples of application security attributes are classified, FOUO, sensitive, etc. Applications maintaining the binding of organization defined security attributes to data must ensure the information attribute associations can be used as a basis for automated policy actions. The integrity of security attribute values is critical to ensuring automated policy actions are performed accurately. Examples of automated policy actions include automated access control decisions (e.g., Mandatory Access Control decisions), or decisions to release (or not release) information (e.g., information flows via cross domain systems).

Description

Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information system and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. Examples of application security attributes are classified, FOUO, sensitive, etc. Applications maintaining the binding of organization defined security attributes to data must ensure the information attribute associations can be used as a basis for automated policy actions. The integrity of security attribute values is critical to ensuring automated policy actions are performed accurately. Examples of automated policy actions include automated access control decisions (e.g., Mandatory Access Control decisions), or decisions to release (or not release) information (e.g., information flows via cross domain systems).

STIG	Date
Database Security Requirements Guide	2012-07-02

Details

Check Text ( C-40682r2_chk )
Review system documentation to determine if the labeling of sensitive data is required under organization defined guidelines. If the labeling of sensitive data is not required, this is NA. Review DBMS vendor documentation to determine whether the DBMS is capable applying security labels with sufficient assurance that the information/label association can be used as the basis for automated policy decisions. If not, this is a finding.

Check Text ( C-40682r2_chk )

Review system documentation to determine if the labeling of sensitive data is required under organization defined guidelines. If the labeling of sensitive data is not required, this is NA.

Review DBMS vendor documentation to determine whether the DBMS is capable applying security labels with sufficient assurance that the information/label association can be used as the basis for automated policy decisions. If not, this is a finding.

Fix Text (F-36096r1_fix)
Utilize a database product capable of applying security labels with sufficient assurance that the information/label association can be used as the basis for automated policy decisions.